This change addresses the use where we are initializing an externally managed mysql server, but which is empty. In this case, we should create the database.

I've implemented the db creation in the tabletserver. This means that ISM also does not need to create the database. However, this change causes ISM to hang (waiting for semi-sync) because the db creation happens before the replicas are pointed at the master. To work around this, I've moved the enforcement of semi-sync until after the db is created.

This change opens up two corner cases, both of which are unlikely in a production environment:

• Between the time that a tablet became master and semi-sync is enforced, an app can rush in and write data that does not meet the durability criteria. This is an unlikely scenario and low risk scenario because we are just initializing the cluster, and everything will converge to the right state after the replicas are wired up.
• A failure in the operation could result in a tablet being master, but semi-sync not being set. In this case, the ISM command will receive an error. This gives the operator the opportunity for an operator to go remedy the system, ideally by doing another reparent.

Finally, this is temporary. Within the next few PRs, ISM will be replaced by a version that happens automatically within vttablet itself.